Already Implemented

• Adding a table with any number of fields:
• Supported field types: Text, Number, Date, Date and Time, Boolean
• Support for primary key fields (including a numeric or time-stamp auto-generated primary key)
• Specifying valid values of fields in one of 4 ways, as in the following examples:
  
  1. Foreign key (reference to a column in a database table or view): Table=Categories, Column=Name
  2. List of valid values: "Bakery", "Dairy"
  3. Range of valid values (Number, Date, Date and Time): Range=[1-5]
  4. Regular Expression (Text): Pattern=\d{1,8}
• Table implementation includes: 
• Automatic creation of the underlying database table 
• Table display on screen 
• Basic data management capabilities ('New', 'Update' and 'Delete')
• Updating a table previously created by the wizard: 
• Renaming the table 
• Renaming and/or changing the type of any field 
• Adding and deleting fields
• Add paging (useful when the underlying database table includes many records)
• Allow starting from an existing database table/view (including the ability to create several views of the same database table/view)
• Support for choosers (fields whose values are restricted to a closed set of values or values appearing in some field in a database table/view) - automatically created when the valid values of a field are defined by a value list or a foreign key

Table Configuration

The table is initialized through the Configuration structure via the Init/Init Configuration process.

The configuration options are:

• Default Optimization
  If set to No, each page query is accompanied by 2 (or in certain cases 1) additional queries which are used to compute the current position and total number of records. This results in a certain performance hit.
  If set to Yes, overall performance is improved, as most page queries are not accompanied with any additional query, and the current position and total are estimated based on previously available data.
• Show Paging Header Group
  Controls visibility of Header Row/Paging Header Group (containing the Number of Records input field and the First, Previous, Next and Last buttons). Conversely controls the visibility of Header Row/Refresh button.
• Number of Records per Page
  Controls the maximum number of records to display at one time. The application user can override this number by entering another value in Header Row/Paging Header Row/Number of Records. If set to 0, all records matching the curent filter are displayed.
  The value is automatically overriden to 0, if both Show Paging Header Group and Show Paging Footer Row are set to No, which results in all records being displayed.
• Show Action Header Group
  Controls visibility of Header Row/Action Group (containing the Add, Update and Delete buttons)
• Show From Filter Row/Show To Filter Row
  Control visibility of the two filter rows (in the table's <Header> element). If only one of the rows is visible then exact filtering will be preformed (simulating the case where To and From rows are identical).
• Number of Pages to Display
  Controls the maximum number of pages to display in the table's <Footer>/Paging Footer Row element, which provides direct access to specific record set pages. If set to 0, the Paging Footer Row is hidden.
• Show Count Footer Row
  Controls visibility of the table's <Footer>/Count Footer Row element, which displays record counts (position and total number of records).

If you wish to change configuration (compared to its initial state) via your own modeling, update the configuration structure, and reuse Init/Init Display.

Next To Do 

1. Add runtime validations (in case valid values are specified, mark the fieild in red if an invalid value is specified) 
2. Support for image fields (e.g. icons)
3. Support for memo fields ('Text Area')
4. Support for hierarchical data structures
5. Automatic management of timestamp fields (<Creation Date>, <Creation Time>, <Last Update Date>, <Last Update Time>) and user identification fields (<Creating User>, <Last Updating User>)